Preventing co-user addition to user definable co-user lists

ABSTRACT

Systems and methods are disclosed for tracking and displaying the logon status of selected co-users of an on-line or network system in real time to a tracking user in a unique graphical interface. The invention provides user definable on-line co-user lists, or “buddy lists,” which track specific co-users in real-time automatically. When a user logs on to a system, one or more of the user&#39;s buddy lists are presented to the buddy list system. The buddy list system attempts to match co-users currently logged into the system with the entries on the user&#39;s buddy list. Any matches are displayed to the user. As co-users logon and logoff, a user&#39;s buddy list is updated to reflect these changes. An indication can also be added to show that a co-user just logged on or just left the system.

BACKGROUND

1. Field of the Invention

This invention relates to on-line communication networks, and particularly to interpersonal communications on such networks.

2. Description of Related Art

An important aspect of an “online” system, such as the proprietary system operated by America Online, Inc. (AOL) or the public Internet system, is knowledge of the people/users/processes on that system and a methodology for communicating with them through some selected protocol. When a person “logs on” to a network system, they are in effect identifying themselves to the system and announcing their presence. On most systems, this presence is unique to every user who is on the system. For example, on the AOL network this presence is known as the “screen name”, but on other systems it could be an Internet Protocol (IP) address or some other unique identifier.

An Internet Service Provider (ISP) is, in a sense, an online system because every user has an associated IP network address and may also have a user id and password. There can also be a hierarchy of logon systems, where an ISP is used to connect to a first network, and then once connected the user can log on to another system with a different identity. These secondary systems can be in parallel (i.e., a user connects to an ISP and then logs on to multiple systems), or a combination of parallel and hierarchical (i.e., a user logs on to multiple systems in parallel once connected to the ISP, and then from one of those parallel systems logs on to yet other systems. Thousands to millions of users may be accessing such complex networks at any point in time.

A problem with networks on any size is tracking personal relationships and maintaining knowledge of the people/users/processes on that system. In the AOL network, a user could use a LOCATE function to inquire from the system if another user was currently logged into the system. In the CompuServe network, a user can use a more limited “WHO'S HERE” function to determine who is present in a forum conference.

The present invention addresses the problem of tracking personal relationships and maintaining knowledge of the people/users/processes on that system with a unique way of establishing and maintaining user definable on-line co-user lists.

SUMMARY

The invention implements a real time notification system that tracks, for each user. the logon status of selected co-users of an on-line or network system and displays that information in real time to the tracking user in a unique graphical interface. The invention provides user definable on-line co-user lists, or “buddy lists”, that track specific co-users in real-time automatically.

A user can create many separate buddy lists of co-users, either with intersecting or disjoint lists of users, and label these buddy lists according to the user's preference. The user can update a buddy list or create new buddy lists whenever necessary. When a user logs on to a system, the user's set of buddy lists is presented to the buddy list system. The buddy list system attempts to match co-users currently logged into the system with the entries on the user's buddy list. Any matches are displayed to the user. As co-users logon and logoff, a user's buddy list is updated to reflect these changes. An indication can also be added to show that a co-user just logged on or just left the system.

The details of the preferred embodiment of the present invention are set forth in the accompanying drawings and the description below. Once the details of the invention are known, numerous additional innovations and changes will become obvious to one skilled in the art.

DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram of a typical network system 10 in which the invention can be implemented.

FIG. 2 a is a set of symbolic data records showing the basic types of data used by one embodiment of the invention for a buddy list, and the conceptual relationship of data elements.

FIG. 2 b is a set of symbolic data records showing the basic types of data used by one embodiment of the invention for a permissions list, and the conceptual relationship of data elements.

FIG. 3 is a graphical display of one implementation of the invention, showing a buddy list window.

FIG. 4 is a graphical display of one implementation of the invention, showing a buddy list setup window.

FIG. 5 is a graphical display of one implementation of the invention, showing a buddy list create window.

FIG. 6 is a graphical display of one implementation of the invention, showing a buddy list preferences window.

FIG. 7 is a graphical display of one implementation of the invention, showing a search member directory window.

FIG. 8 is a graphical display of one implementation of the invention, showing a member location window.

FIG. 9 is a graphical display of one implementation of the invention, showing an instant message window.

FIG. 10 is a graphical display of one implementation of the invention, showing a buddy chat window.

FIG. 11 is a flowchart showing an implementation of the invention.

Like reference numbers and designations in the various drawings indicate like elements.

DETAILED DESCRIPTION

Throughout this description, the preferred embodiment and examples shown should be considered as exemplars, rather than as limitations on the present invention.

Overview

The invention implements a real time notification system that tracks, for each user, the logon status of selected co-users and displays that information in real time to the tracking user in a unique graphical interface. The invention provides user definable on-line co-user lists, or “buddy lists”, that track specific co-users in real-time automatically. Such automatic monitoring is significant, because in a system of any size there would be no way for a user to track the comings and goings of thousands or millions of users each moment in time.

An important component of the buddy list system is that a user can create many separate buddy lists of co-users, either with intersecting or disjoint lists of co-users, and label these buddy lists according to the user's preference. The user can update a buddy list or create new buddy lists whenever necessary. When a user logs on to a system, the user's set of buddy lists is presented to the buddy list system. The buddy list system attempts to match co-users currently logged into the system with the entries on the user's buddy list. Any matches are displayed to the user. As co-users logon and logoff, a user's buddy list is updated in real-time (or near real-time, taking into account network and processing delays) to reflect these changes. An indication can also be added to show that a co-user just logged on or just left the system.

Hardware System

By way of example only, FIG. 1 is a block diagram of a typical network system 10 in which the invention can be implemented. The network system 10 includes a plurality of user stations 12 that preferably include a processor chassis 14 having a network link. The network link is for receiving and transmitting data in analog or digital form over a communications link 16, such as a serial link, local area network, wireless link, parallel link, etc. Also coupled to a typical processor chassis 14 is a display 18, a keyboard 20, and a pointing device 22 (e.g., a mouse).

The communications link 16 couples each user station 12 as a “client” to a logon system 24, which is typically a software program executing on a remote server somewhere on a network. The logon system 24 communicates with a “Buddy List System” 26, which is preferably a software program executing on a server somewhere on the network. The Buddy List. System 26 maintains a database 28 for storing user information. The database 28 may be of any type, such as relational or hierarchical, and may be centralized or distributed. For example, the database 28 may be stored at least in part on each user's own station 12. In such a case, the database 28 contents would be transmitted to the Buddy List System 26 when the user logged into the system.

Data Structure

FIG. 2 a is a set of symbolic data records showing the basic types of data used by the Buddy List System 26, and the conceptual relationship of data elements. A Group Name table 30 stores user-defined group names for buddy lists. Each user may define multiple buddy lists by group names (two being shown by way of example). Each group name in the Group Name table 30 has an associated Buddy List table 32, comprising multiple records. Each Buddy List table 32 record corresponds to a co-user (“buddy”) that the user wishes to track. In the preferred embodiment, the record includes data elements for the screen name (or address, such as an Internet address) of a particular co-user to be tracked, and the logon status of that user (e.g., codes for “In” or “Out”).

FIG. 2 b is a set of symbolic data records showing the basic types of data used by one embodiment of the invention for a Permissions List 34, and the conceptual relationship of data elements. Each user in the system has an associated Block Status code. If a user's Block Status code is equivalent to “none”, then no co-user may enter that user into the co-user's buddy lists. If a user's Block Status code is equivalent to “all”, then all co-users may enter that user into their buddy lists. If a user's Block Status code is equivalent to “all except”, then all co-users except those entered in a linked Exclusion List 36 may enter that user into their buddy lists. If a user's Block Status code is equivalent to “none except”, then only co-users entered in a linked Inclusion List 38 may enter that user into the co-user's buddy lists. In one embodiment, a user may only have one of an Inclusion List 36 and an Exclusion List 48.

Example Implementation

FIG. 3 is a graphical display of one implementation of the invention, showing a Buddy List window 40 with a buddy list named “Home List” in a large scrollable area. Buddy list names are like categories. Other buddy lists can be shown in the same display. Indented underneath each buddy list are the names (or addresses) of user-selected co-users comprising that list. In the example shown, the “Home List” includes three co-users and their status as “IN” (i.e., currently logged into the system) or “OUT” (i.e., currently logged out of the system). Any desired method or technique cart be used to indicate log status, such as distinct attributes (e.g., bolding a name to indicate logged in, graying a name to indicated logged out) or other symbols (e.g., checkmarks to indicate logged in), etc. In still another embodiment, only logged in members of a buddy list are displayed. In one embodiment, an asterisk or other symbol appears next to the screen name of the most recent co-user to log into the system, and parentheses are placed around the screen name of the most recent co-user to log out of the system.

In the preferred embodiment, a user can “minimize” a buddy list to suppress display of all the co-users in that group. This is preferably implemented so that a double click on the buddy list name will cause all the screen names listed beneath to disappear. In the preferred embodiment, minimized buddy lists are indicated by a “+” symbol next to the buddy list name. Double-clicking on the buddy list name again displays all of the hidden co-users under that name. A user can also keep tabs on each list by checking out the numbers posted in parenthesis next to the buddy list names. This number tells the user how many people on that list are logged in out of the total number of screen names on the buddy list. In the illustrated example, ⅔ means that two of the three people on the “Home List” are currently online.

In the preferred embodiment, when the user first logs into the system, the Buddy List window 40 opens, informing the user which of the user's buddy list members are currently online. The user can either close this window, or leave it open while visiting other areas of the system. If the Buddy List window 40 is left open, the user has a current, real-time list of all the user's buddies in who are online at any particular moment.

The illustrated Buddy List window 40 shows a number of buttons for setting up or using buddy lists. Included buttons in the preferred embodiment are: LOCATE, for determining which “chat room” a buddy is in at a particular moment; IM, for sending an “Instant Message”; SETUP, for creating and editing buddy lists or setting buddy list preferences; and BUDDY CHAT, for inviting buddies to a private chat or a favorite place in the system.

Setup

FIG. 4 is a graphical display of one implementation of the invention, showing a Buddy List Setup window 50 with a buddy list named “Home List” in a scrollable area. Buttons are provided for creating a new buddy list; editing a selected buddy list; deleting a buddy list; viewing the members of a selected buddy list; accessing a Member Directory for the system; and accessing a preferences windows. In the preferred embodiment, each buddy list is shown in the scrollable area with a count of the number of co-users in each list.

FIG. 5 is a graphical display of one implementation of the invention, showing a Buddy List Create window 60. A user can enter a buddy list group name and a screen name for each co-user to be tracked. A list of buddies on a particular list are also displayed, along with a button allowing removal of an existing buddy. After entry of all necessary data in such a window, the user's Group Name table 30 and the appropriate Buddy List table 32 are updated using conventional data processing techniques, Editing a buddy list can be done from the same or a similar window.

FIG. 6 is a graphical display of one implementation of the invention, showing a Buddy List Preferences window 70. In the preferred embodiment, these Preferences include the following:

-   -   Show me my Buddy List(s) immediately after I sign onto AOL. This         option opens the Buddy List window 40 (FIG. 3) when the user         logs on to the system.     -   Play sound when buddies sign-on. This option enables a sound to         play when one of the co-users on a user's buddy list program         logs on (“BuddyIn”).     -   Play sound when buddies sign-off. This option enables a sound to         play when one of the co-users on a user's buddy list program         logs off (“BuddyOut”).     -   Allow all members to add me to their lists/invitations. This         option grants permission for all co-users to add the user to         their buddy lists and send the user “Buddy Chat Invitations” and         other information. If set, the appropriate user record in the         Permissions List table 34 is marked with a code for “all” in the         Block Status field.     -   Block all members from adding me to their lists/invitations.         This option restricts all co-users from adding the user to their         buddy lists and from sending the user “Buddy Chat Invitations”         and other information. If set, the appropriate user record in         the Permissions List table 34 is marked with a code for “none”         in the Block Status field.     -   Allow only the members below. This option restricts all members         from adding the user to their buddy lists and from sending the         user “Buddy Chat Invitations” and other information, except for         those co-users specifically listed where provided in the window.         If set, the appropriate user record in the Permissions List         table 34 is marked with a code for “none except” in the Block         Status field, and an Inclusion List 38 is linked to the user for         storing the names of included co-users.     -   Block only the members below. This option grants permission for         all other members to add the user to their buddy lists and send         the user “Buddy Chat Invitations” and other information, except         for those co-users specifically listed where provided in the         window. If set, the appropriate user record in the Permissions         List table 34 is marked with a code for “all except” in the         Block Status field, and an Exclusion List 36 is linked to the         user for storing the names of excluded co-users.     -   Sound Library. Allows a user to select sound events for         “BuddyIn” and “BuddyOut”.

In the preferred embodiment, the Inclusion List 38 and the Exclusion List 36 options are mutually exclusive. In this way, a user can control who sees the user logging on and off the system. Although the user can be placed on the buddy list of a co-user, if the user blocks visibility through the use of these controls, the co-user does not see the logon/logoff status of that user.

FIG. 7 is a graphical display of one implementation of the invention, showing a Search Member Directory window 80. In the preferred embodiment, this feature is accessed from the Buddy List Setup window 50 (FIG. 4), and allows searching a system directory in known fashion for screen names or addresses of co-users, for entry into buddy lists.

Locate

FIG. 8 is a graphical display of one implementation of the invention, showing a member location window 90. In the preferred embodiment, this feature is accessed from the Buddy List window 40 (FIG. 3). Selecting a co-user's name from a buddy list and activating the LOCATE button will cause the system to determine whether the selected co-user is in a chat area or not. If no co-user is selected and the LOCATE button is activated, a member location window 90 is displayed with the input field blank, for entry of a co-user name. This feature using the existing locate functions of the system.

Instant Messages

Once a co-user is displayed on a user's buddy list, indicating that the co-user is currently logged into the network system, the preferred embodiment of the invention enables a simple way of communicating with that co-user. FIG. 9 is a graphical display of one implementation of the invention, showing an Instant Message window 100. In the preferred embodiment, the Instant Message window is automatically displayed by activating (e.g., by clicking or double clicking) a co-user's name on a buddy list. The “To:” line of the window is pre-filled with the selected co-user's name and the cursor is positioned in the text entry area ready for text to be typed to be sent to the targeted co-user. The Instant Message function can also be activated by highlighting a co-user name in the buddy list and clicking on the IM button in the Buddy List window 40 (FIG. 3).

Buddy Chat

FIG. 10 is a graphical display of one implementation of the invention, showing a Buddy Chat window 110. As implemented on the AOL on-line system, the Buddy Chat function can be used to send an invitation to one or more co-users to a private “chat room” or a favorite place in the system. In the preferred embodiment, this function can be initiated by selecting a co-user name and activating the BUDDY CHAT button in the Buddy List window 40 (FIG. 3). The Buddy Chat window 110 is displayed, allowing the user to add additional names to the Screen Names to Invite field either manually or by selecting additional names from the Buddy List window 40 and again activating the BUDDY CHAT button. A message can be sent to each invitee via the Message to Send field. In the preferred embodiment, an entire buddy list group can be added to the Buddy Chat window 110 by selecting a group name from the Buddy List window 40 and activating the BUDDY CHAT button or double-clicking.

To talk privately with the selected co-users, the user selects the Private Chat Room radio button and enters a “Buddy Chat Room Name” in the provided edit box. If the edit box is left blank, a Buddy Chat Room Name is automatically created for the user. Upon selecting Send, each selected co-user will receive a message inviting them to access and display a Buddy Chat Room (chat rooms are an existing feature of the AOL system).

To share those places a user likes hest on the AOL system, the user selects the Keyword/Favorite Place radio button and enters a “Keyword” (i.e., a shortcut word defining an address) to a system site in the provided edit box, either manually or by using a “drag and drop” action from a list of the user's favorite places in the system. Upon selecting Send, each selected co-user will receive a message inviting them to access and display that online site.

FIG. 11 is a flowchart showing an implementation of the invention. A User logs in to a Logan System in conventional fashion (Step 200). The Logon System performs normal logon procedures (e.g., requesting a user ID and/or a password) and notifies the Buddy List System about the User (i.e., passes the User's ID, address, or screen name to the Buddy List System) (Step 202). The Buddy List System accesses that User's Buddy Lists from a database, which may be, for example, on the user's station 12 (Step 204). The entries in the User's Buddy Lists are then compared to the records of the Logan System (Step 206). This step is shown in dotted outline to indicate that the comparison can be done by passing records from the Logon System to the Buddy List System, or vice versa, or could be done a separate system. The Buddy List System then displays a Buddy List window showing the status (i.e., logged in or not) of the co-users on the User's Buddy Lists with any of various indicator markings (Step 208).

Thereafter, while the User's Buddy List window is open, the Logon System notifies the Buddy List System about new logons/logoffs of co-users (Step 210), causing a new compare of the User's Buddy List entries to the Logon System records (Step 206). Again, the compare may be performed anywhere. For example, the Logon System may maintain a copy of a User's Buddy Lists, and notify the Buddy List System only upon a logon status change for a co-user on the User's Buddy Lists. The Buddy List System then updates the indicated status of the displayed co-users (Step 208).

Software Implementation

The invention may he implemented in hardware or software, or a combination of both. However, preferably, the invention is implemented in computer programs executing on programmable computers each comprising at least one processor, at least one data storage system (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. Program code is applied to input data to perform the functions described herein and generate output information. The output information is applied to one or more output devices, in known fashion.

Each program is preferably implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the programs can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language.

Each such computer program is preferably stored on a storage media or device (e.g., ROM or magnetic diskette) readable by a general or special purpose programmable computer, for configuring and operating the computer when the storage media or device is read by the computer to perform the procedures described herein. The inventive system may also be considered to be implemented as a computer-readable storage medium, configured with a computer program, where the storage medium so configured causes a computer to operate in a specific and predefined manner to perform the functions described herein.

A number of embodiments of the present invention have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the invention. For example, while the preferred embodiment is event driven, meaning that updates to a buddy list are based on a change in the logon status of all co-users or of the selected co-users on a user's buddy list, updates can instead be performed on a periodic basis, where the buddy list system polls the logon system for logon status changes, or vice versa. Accordingly, it is to be understood that the invention is not to be limited by the specific illustrated embodiment, but only by the scope of the appended claims. 

1. (canceled)
 2. (canceled)
 3. (canceled)
 4. (canceled)
 5. (canceled)
 6. (canceled)
 7. (canceled)
 8. (canceled)
 9. (canceled)
 10. (canceled)
 11. (canceled)
 12. (canceled)
 13. (canceled)
 14. (canceled)
 15. A method comprising: maintaining, in a non-transitory computer readable storage medium, a first list of co-users associated with a first user of a communications system; maintaining, in the non-transitory computer readable storage medium, a second list of co-users associated with a second user of the communications system; receiving an indication from the first user to block the second user from adding the first user to the second list; and preventing, using at least one processor, the addition of the first user to the second list.
 16. The method as recited in claim 15, wherein receiving the indication comprises receiving a request from the first user to block the second user.
 17. The method as recited in claim 15, further comprising a list of co-users selected to be blocked by the first user.
 18. The method as recited in claim 17, wherein receiving the indication comprises receiving an indication that the first user has added the second user to the list of co-users selected to be blocked by the first user.
 19. The method as recited in claim 15, wherein receiving the indication comprises receiving an indication from the first user to block all co-users from adding the first user to lists of co-users associated with other users of the communications system.
 20. The method as recited in claim 15, further comprising preventing the first user from receiving messages sent from the second user.
 21. The method as recited in claim 15, wherein the first list of co-users comprises co-users selected by the first user.
 22. The method as recited in claim 15, further comprising presenting a graphical display of the first list of co-users to the first user when the first user logs into the communications system.
 23. The method as recited in claim 22, further comprising indicating on the graphical display of the first list whether at least one co-user on the first list is currently logged into the communications system.
 24. The method as recited in claim 0, wherein indicating on the graphical display of the first list whether at least one co-user on the first list is currently logged into the communications system comprises placing a symbol next to a name of the at least one co-user on the graphical display of the first list.
 25. The method as recited in claim 22, further comprising indicating on the graphical display of the first list a status of at least one co-user on the first list.
 26. A non-transitory computer-readable storage medium including a set of instructions that, when executed, cause at least one processor to perform steps comprising: maintaining a first list of co-users associated with a first user of a communications system; maintaining a second list of co-users associated with a second user of the communications system; receiving an indication from the first user to block the second user from adding the first user to the second list; and preventing the addition of the first user to the second list.
 27. The computer-readable storage medium as recited in claim 26, wherein receiving the indication comprises receiving a request from the first user to block the second user.
 28. The computer-readable storage medium as recited in claim 26, further comprising instructions that, when executed, cause the at least one processor to maintain a list of co-users selected to be blocked by the first user.
 29. The computer-readable storage medium as recited in claim 28, wherein receiving the indication comprises receiving an indication that the first user has added the second user to the list of co-users selected to be blocked by the first user.
 30. The computer-readable storage medium as recited in claim 26, wherein receiving the indication comprises receiving an indication from the first user to block all co-users from adding the first user to lists of co-users associated with other users of the communications system.
 31. The computer-readable storage medium as recited in claim 26, further comprising instructions that, when executed, cause the at least one processor to block messages sent from the second user to the first user.
 32. The computer-readable storage medium as recited in claim 26, wherein the first list of co-users comprises co-users selected by the first user.
 33. The computer-readable storage medium as recited in claim 26, further comprising instructions that, when executed, cause the at least one processor to present a graphical display of the first list of co-users to the first user when the first user logs into the communications system.
 34. The computer-readable storage medium as recited in claim 26, further comprising instructions that, when executed, cause the at least one processor to indicate on the graphical display of the first list whether at least one co-user on the first list is currently logged into the communications system.
 35. The computer-readable storage medium as recited in claim 0, wherein indicating on the graphical display of the first list whether at least one co-user on the first list is currently logged into the communications system comprises placing a symbol next to a name of the at least one co-user on the graphical display of the first list.
 36. The computer-readable storage medium as recited in claim 33, further comprising instructions that, when executed, cause the at least one processor to indicate on the graphical display of the first list a status of at least one co-user on the first list.
 37. A system comprising: at least one non-transitory computer readable storage medium; and at least one processor programmed to: maintain, in the at least one non-transitory computer readable storage medium, a first list of co-users associated with a first user of a communications system; maintain, in the at least one non-transitory computer readable storage medium, a second list of co-users associated with a second user of the communications system; and prevent the addition of the first user to the second list upon receiving an indication from the first user to block the second user.
 38. The system as recited in claim 37, wherein receiving the indication comprises receiving a request from the first user to block the second user.
 39. The system as recited in claim 37, wherein the at least one processor is further programmed to maintain, in the at least one non-transitory computer readable storage medium, a list of co-users selected to be blocked by the first user.
 40. The system as recited in claim 39, wherein receiving the indication comprises receiving an indication that the first user has added the second user to the list of co-users selected to be blocked by the first user.
 41. The system as recited in claim 37, wherein receiving the indication comprises receiving an indication from the first user to block all co-users from adding the first user to lists of co-users associated with other users of the communications system.
 42. The system as recited in claim 37, wherein the at least one processor is further programmed to block messages sent from the second user to the first user.
 43. The system as recited in claim 37, wherein the first list of co-users comprises co-users selected by the first user.
 44. The system as recited in claim 37, wherein the at least one processor is further programmed to present a graphical display of the first list of co-users to the first user when the first user logs into the communications system.
 45. The system as recited in claim 37, wherein the at least one processor is further programmed to indicate on the graphical display of the first list whether at least one co-user on the first list is currently logged into the communications system.
 46. The system as recited in claim 0, wherein indicating on the graphical display of the first list whether at least one co-user on the first list is currently logged into the communications system comprises placing a symbol next to a name of the at least one co-user on the graphical display of the first list.
 47. The system as recited in claim 44, wherein the at least one processor is further programmed to indicate on the graphical display of the first list a status of at least one co-user on the first list. 